feat(iptv): support multiple configurable Stalker portals with per-portal groups - #607

Wiederhergestellt aus den alten Branches (beim Fork-Aufräumen 22.08. verloren gegangen).
Baut eine DEBUG-APK via assembleSideloadDebug mit Application-ID-Suffix .stalker-live
(parallel installierbar neben produktiver ARVIO). Braucht keine Secrets.
Wird vor dem upstream-PR wieder entfernt.

Co-authored-by: openhands <openhands@all-hands.dev>

Co-authored-by: openhands <openhands@all-hands.dev>

Reworks Stalker from a single config object (stalkerPortalUrl /
stalkerMacAddress) into a real list of up to 3 StalkerPortalEntry items,
mirroring the M3U playlists model. This is the invisible backend foundation
for the multi-portal UI; the existing single Stalker settings row stays
functional via the first portal.

Data model & persistence:
- IptvConfig.stalkerPortals: List<StalkerPortalEntry>
- IptvCloudProfileState.stalkerPortals replaces the two legacy fields
- DataStore stalkerPortalsKey() stores JSON (analogous to playlistsKey())
- Legacy migration: old single-portal fields auto-become "Portal 1"
  (id stalker1) when the list store is empty

Playback & loading:
- cachedStalkerApi -> cachedStalkerApis Map<portalId, StalkerApi>
- resolveStalkerStreamUrl(channelId, command) routes by stalker:<portalId>:
  prefix; falls back to the first portal for legacy callers
- Channel ids prefixed stalker:<portalId>:<origId> so startsWith("stalker:")
  checks keep matching; all enabled portals load in parallel and merge

Signatures & sync:
- buildConfigSignature/buildSourceSignature and cloud/sync signatures
  derived from the portal list (version bumped to invalidate stale caches)
- Cloud sync exports/imports the portal list; legacy keys cleared on import

Compatibility: SettingsUiState exposes iptvStalkerUrl/iptvStalkerMac as
derived getters over portals[0] so the Session-1 settings UI is unchanged.

Unit tests cover migration, multi-portal prefix extraction, JSON round-trip,
max-portal cap, and blank-field filtering.

Co-authored-by: openhands <openhands@all-hands.dev>

Kotlin could not infer the type parameters for the empty fallback pairs
and success-branch Triples in the parallel Stalker-portal merge paths.
Make the Triple<String, StalkerApi?, List<IptvChannel>> and
emptyMap/emptyList fallbacks explicit so compileSideloadDebugKotlin succeeds.

Co-authored-by: openhands <openhands@all-hands.dev>

…date

When the versionCode stayed at 310 Android refused to install a new test
APK over the existing .stalkerlive build (same version), forcing a full
reinstall that would wipe the saved Stalker portal and defeat the
migration test. Each test build now derives a unique, monotonically
increasing versionCode (310 + github.run_number) so updates install
in place. Workflow-only change, removed before the upstream PR.

Co-authored-by: openhands <openhands@all-hands.dev>

Debug APKs built in CI each get a different ephemeral signing key, so
Android refuses in-place updates (signature mismatch). This generates a
fixed debug keystore once, to be stored as a repository secret and reused
by test-apk builds.

Co-authored-by: openhands <openhands@all-hands.dev>

Debug APKs built in ephemeral CI runners each get a different signing
key, so Android refuses to update one test build over another (signature
mismatch), regardless of versionCode. Store a fixed debug keystore in the
branch and copy it to ~/.android/debug.keystore before building so every
test APK is signed with the same key and can update in place.

The keystore uses the standard debug password and is removed (along with
test-apk.yml) before the upstream PR.

Co-authored-by: openhands <openhands@all-hands.dev>

getMemoryCachedSnapshot() and getCachedSnapshotOrNull() built the
IptvSnapshot without hiddenGroups/groupOrder, leaving them at the
emptyList() default. The TV grid reads these cached snapshots at
startup (and onChannelsReady reuses the live snapshot's hiddenGroups),
so the hidden-group filter had nothing to apply and every group became
visible again. Read both prefs from the DataStore the same way
loadSnapshot already does.

… categories

Session 2 — full Stalker portal UI (TV + Mobile):

SettingsScreen:
- Two separate sections (M3U Playlists + Stalker Portals)
- Up to 3 Stalker portal rows with full chip row
  (categories / enable / edit / rename / up / down / delete)
- 'Add Stalker portal' button disabled at max (3)
- Rename dialog (name editable, subtitle 'Stalker', no EPG counter)
- Per-portal categories dialog with per-portal bulk-toggle
- Enable/disable as icon (same style as M3U, no slider)
- Sort up/down within Stalker section only

D-Pad navigation:
- Recomputed index dispatch maps for variable M3U + Stalker row counts
- iptvRowMaxAction() replaces stalkerRowMaxAction() (both rows = 5 chips)
- firstIptvGroupIndex() accepts stalker portal ids for per-portal bulk-toggle
- sectionMaxIndex includes Stalker portal count

SettingsViewModel:
- Removed compat getters (iptvStalkerUrl/iptvStalkerMac)
- Real CRUD: onAddStalkerPortal, onEditStalkerPortal, onToggleStalkerPortal,
  onMoveStalkerPortalUp/Down, onRemoveStalkerPortal, onRenameStalkerPortal
- loadIptvGroupsForPlaylist is stalker-portal-aware (stalker:<portalId>: prefix)

IptvRepository:
- saveStalkerPortals() added (normalize, cap at 3, clear removed portal groups)
- STALKER_PLAYLIST_ID / MAX_STALKER_PORTALS in public companion object

strings.xml: new section title, portal-N template, content descriptions,
bulk-toggle labels, rename dialog strings

Tests: normalizeStalkerPortalEntry + D-Pad index helper unit tests

Co-authored-by: openhands <openhands@all-hands.dev>

…constants

Two companion objects in one class is illegal in Kotlin — the compiler
silently dropped the private one, making MULTI_SPACE_REGEX/HTTP_URL_REGEX
unresolved. Move the public constants to top-level in StalkerPortalSupport.kt
and keep the private companion object intact.

Co-authored-by: openhands <openhands@all-hands.dev>

MobileSettingsSubPage has its own local Stalker state vars; the input/rename
dialogs must live in that function, not in MobileCloudAccountSubPage where
the vars are unresolved.

Co-authored-by: openhands <openhands@all-hands.dev>

The mobile Stalker portal row previously rendered the full TV chip
row (categories, toggle, edit, rename, up, down, delete = 7 controls),
causing overflow/clipping on touch devices. Mirror the M3U mobile
row instead: show only the category selector and enable/disable
toggle, with tap-to-edit and long-press selection mode for reorder
(drag handle) and delete. TV rows and D-pad index maps are unchanged.

Hidden groups for Stalker portals are stored under the portal id
(e.g. `stalker1|group`), but the touch channel list derived the
playlist id from `channel.id.substringBefore(':')`, which yields the
literal `stalker` prefix for `stalker:<portalId>:<origId>` ids. The
resulting `stalker|group` key never matched the stored `stalker1|group`
key, so hidden Stalker groups stayed visible on phones.

Resolve the playlist id for hidden-group keys via the Stalker portal
segment (reusing StalkerPortalSupport.portalIdFromChannelId) and fall
back to substringBefore(':') for M3U/Xtream ids. Apply this in
buildCategoryIndex/buildCategoryTree/buildPagedStartupChannelState and
the search filter, leaving category-id/sidebar keys unchanged.

Also match the mobile Stalker row to M3U: LiveTv leading icon and the
portal URL as subtitle.

Align the TV Stalker portal row with the M3U row: a leading LiveTv
icon and the portal URL as subtitle (instead of the literal "Stalker"
label). Apply the same leading icon to the TV M3U row for visual
parity. Icons are decorative, so the D-Pad index dispatch maps and
focus slots are unchanged.

Drop the now-unused settings_stalker_subtitle string resource.

Drop the fork-only test-apk.yml workflow and the committed debug
keystore under .github/test-signing/, plus the now-obsolete gitignore
exception that whitelisted it. These were development-only helpers
for building sideload debug APKs and must not ship in the upstream PR.